The Atari Compendium

home *** CD-ROM | disk | FTP | other *** search

/ The Atari Compendium / The Atari Compendium (Toad Computers) (1994).iso / files / umich / telecomm / transbbs.lzh / TRANSBBS.DOC < prev next >

Wrap

Text File | 1992-07-17 | 42.1 KB | 1,057 lines

Transcendence BBS (c) Copyright 1992 Twilight Zone Software Programming by David Brown & Wayne Watson All rights reserved DOCUMENTATION NOTICE At this time the documentation is not complete. If you have purchased Transcendence, the documentation will be mailed to you at no further charge, when completed. This file is quite verbose, so expect to have some unanswered questions. For your convenience, there are four support boards and a voice number, incase you have some questions. You may also mail questions to Twilight Zone Software. Twilight Zone Software P.O. Box 7264 Louisville, KY 40257 (502) 897-1582 (Voice support, David Brown: EST noon-9:00pm) (502) 897-1589 (Data, HST 9600) (803) 879-4186 (Data, v.32bis 9600) (502) 245-0386 (Data, v.32 9600) COPYRIGHT NOTICES The Transcendence BBS program (TRANSBBS.PRG, KEYCODE.DAT), and this manual are copyrighted by Twilight Zone Software. Unauthorized reproductions of those files, or the manual is strictly prohibited by international copyright laws. This software is not allowed to be "rented" or "borrowed", such acts are clearly a violation of copyright laws. We reserve the right to deny updates & support to anyone, for disobeying the copyright. We have always provided you with a non-copyprotected BBS package, with the hopes that you will not distribute it without our written permission. "Pirating" software, as illegal copying is often called, only hurts the authors of the program, and those who paid for the program. Please do your part and do not support software piracy. BE WARNED! In development of the Transcendence BBS package, we have attempted to create a bug-free system, with no harmful side affects. Unfortunately, with a program of this size, it is impossible for us to predict every configuration a sysop could create. Due to this we must ask you to use the software with your own risk. We can not be held reasonable for damage (Or loss) of data, hardware or software. CREDITS In the development of this BBS system we have had help from many, many people. For those of you who are not mentioned, I offer my apologies. We thank Greg Xynides for the endless hours he spent beta testing early versions of the BBS. Even today he still sends us full reports on anything we have forgotten, or messed up. Jeff White wrote the 68000 code we use for CRC-16 testing. This code has proven to be fast, effective, and bug-free. We also would like to thank everyone who has offered ideas, suggestions, and who has taken the time to let us know what we were doing wrong. There are too many of you to name here, but you know who you are. TRANSCENDENCE HISTORY The Transcendence BBS package was original conceived by David Brown in 1986. He began researching BBS programs, how they work, and how they don't work. At this time he did not know the first thing about computer programming (His first computer was a 520ST, in Oct. 1985). He began teaching himself how to write this type of software by programming online door software. In mid 1987 he began work on the "STark" BBS program. Soon he was joined by Jason Dickens. They worked on the program for about 2 years, and due to legal complications had to terminate their joint-effort. For a one year period David was without the source code to the STark BBS program. Since BBS programming was his work away from work, he started a new one. This program was entitled "STairway" (It was never completed). He then obtained the source code to STark, and used the two programs to create what is now "Transcendence." Soon after starting on Transcendence started, Wayne Watson began re-writing many of the old STark routines. Since Wayne & David started working together, they have never stopped to take a breath. The program has gone through massive rewrites and modifications. The current program we have is beyond what we ever thought we could do. We feel that we have succeeded in creating the most flexible, powerful, user-friendly, and sysop- friendly BBS system ever. Our sysops seem to agree. TRANSCENDENCE SUPPORT One of the main benefits to the Transcendence BBS system is our support. All updates to our software are 100% free. You pay only the phone bill, or postage. We are planning a moduler version of the BBS system, there will be a minimal update fee for this, but it will be a one time fee. We rely on our sysops to give us feedback on the program. Ninety percent of the features in the software are features requested by one of our sysops. Unlike other software, we actually listen to our clients. You can obtain your free updates by calling one of our support BBSs, or by mailing a Self-Addressed-Stamped-Envelope, with a disk enclosed, to our post office box. We encourage you to give us suggestions. We can only improve the program if you let us know how. We also need to know if something is not working correctly. If you find any "bugs" in the software, let us know. We can't fix 'em, if we can't find 'em! Twilight Zone Software P.O. Box 7264 Louisville, KY 40257 (502) 897-1582 (Voice - 11:00am - 10:00pm Monday thru Friday EST) (502) 897-1589 (Support Line One: 14.4k Supra v.32bis) (804) 879-4186 (Support Line Two: 14.4k Supra v.32bis) CHAPTER ONE: Getting Started SYSTEM REQUIREMENTS To run the Transcendence BBS System you need the following hardware: o 520, 1040, Mega ST, STe, or TT o At least 1 meg of RAM o A modem (Hayes Compt. preferably) o A hard drive with at least 20 megs of space o Color or MONOchrome monitor (Medium & high resolution only) The following software/hardware is preferable, but not required: o Printer o XYZ external Zmodem protocol o Software or hardware backup utility o Micro Emacs Editor (Remote version) PREPARING TO CREATE YOUR BBS SYSTEM There are many things to consider before you begin the installation process. Many new sysops overlook these details, we hope we can prevent you some heartache down the road. The Transcendence BBS System takes up a lot of Hard Drive Space. Before installing the BBS you must make sure you have enough hard drive space. To do this, delete old files you do not need, copy files you do not use often to floppy. If you were to create a BBS allocated for 100 users and five message bases (100 messages each, 20 lines long), that would take about 2-3 megs of hard drive space. Hopefully that will give you some idea of how much room you will need. You can tell the BBS System what partitions to use for each type of data it creates/uses. For example, you can have your download files on drive C & D, your message base files could be on drive F, and all other files on drive H. While you clear off your hard drive space take into consideration where you want your different types of data. You can use the same partitions for all of the data files the BBS uses, or use many different ones, it all depends on what you want. Transcendence uses "Pre-Allocated" data storage. That is, whenever possible the BBS makes all data files to their full size. This makes file access faster, and reduces the chance of DISK FULL errors (No BBS can prevent DISK FULL errors, only the Sysop can!). Whenever Transcendence has to create a file, it picks the drive with the most space (assuming you have it set up to use more than one drive). The next big step is to think about how you want your BBS to be setup. Decide on what types of message bases you want, and what types of file areas you want. We suggest writing this information down, you will need it soon. Now make sure you have enough disk space, and have prepared a list of message bases & file areas, and lets get started creating your BBS! THE MASTER DISK Within this documentation you should have received a disk. The disk is in DS/DD format. If you can not read that type of disk, contact Twilight Zone Software to get a replacement. Before doing anything else, make a backup copy of your master disk. Use the backup when possible, store the original for safekeeping. If you have trouble creating a backup copy of your original disk consult your Atari owners manual for "Duplicating" disks. YOUR KEYCODE.DAT FILE The file called KEYCODE.DAT is a private-key type of file. In this file is your name, and serial number. This file is not to be given out to anyone, for any purpose. If someone gets a copy of your KEYCODE.DAT file please contact Twilight Zone Software for a replacement copy. (We can prevent 'stolen' KEYCODE.DAT files from working.) CHAPTER TWO: Creating your BBS INTRODUCTION TO THIS CHAPTER In this chapter we are going to explain how to install a complete bulletin board system. After reading this you should feel comfortable with your own BBS installation. Please remember that the Transcendence Bulletin board System is loaded with options, and the way we are setting up this bulletin board may be different from the way you want to set up your own bulletin board. We have attempted to explain all of the options in great detail. OUR BBS DESIGN As described in the previous chapter, we have made a list of message bases we want, file areas, etc. The following is a list of things you might want to consider before you install your own bulletin board. Please remember, this is only an example, you can make your BBS anyway you want! (Enclose the following in a box): Message bases: General BBS chatter : 100 Msgs max., 20 lines each. Atari ST : 100 Msgs max., 15 lines each. Local Atari club : 250 Msgs max., 15 lines each. Endless story : 500 Msgs max., 20 lines each. "Anonymous" msgs : 50 Msgs max., 20 lines each. Computer wars : 100 Msgs max., 10 lines each. High Access Users : 50 Msgs max., 10 lines each. File areas: Atari ST games : 5 line descriptions Atari ST utilities : 10 line descriptions Atari ST misc. : 5 line descriptions Text files : 5 line descriptions Pictures/ART : 5 line descriptions Sysops only : 5 line descriptions Data storage: DATA files : Drives C,D MESSAGE files : Drive E TEXT files : Drive E FILE area files : Drives C,D,E FMAIL files : Drives D,E BACKUP files : Drive F MODULES files : Drive F TEMP files : Drive C Main BBS partition: C. Main BBS folder name: TRANS (End of setup box) You can have up to 256 message bases, and 256 file areas. The BBS program will also access all of your hard drive partitions (Or only a certain number of them). We suggest you make a similar list, with the message bases you want, file areas, and where you want your different types of data. The 'main BBS partition' is the drive you will be running your BBS from. Transcendence creates all of its data inside of folders. We suggest you use "TRANS" for your main folder. If you do use "TRANS" then you will have a folder named "TRANS" on each partition you define for the BBS to use. Inside of that folder will be more folders for the various types of data. If you prefer you can not have a MAIN folder, in that case all of your other folders would be in the root directory. We prefer using a main folder since it does not clutter your partitions with lots of folders in the root directories. BEGINNING THE INSTALLATION Place the backup of your master disk into drive A (You better had made a backup!). By now you should have decided on your main partition, and main BBS folder name. If you are going to use "TRANS" as your main folder name simply copy the entire "TRANS" folder from your master disk, to the root directory of the partition you will be running the BBS from. The will copy the folder, and all of the files as well. If you prefer to use a different main BBS folder name then CREATE a folder with that name on your main BBS partition. Open the "TRANS" folder on your master disk and copy all of the files into your main BBS folder. In our example we simply copied the "TRANS" folder onto drive (partition) C. Now open the main BBS folder (If it isn't already). You should see quite a few filenames. The only one to worry about now is the "SYSEDITG.PRG". This is the System Editor. It will create almost all of the data you need to run your BBS system. Execute this program by double-clicking on its icon, or filename. You will be presented with an information box (fig. 1), press [Return] and the system editor will load some data, and then present you with a file-selector box. The system editor is looking for the "TRANS.DAT" file, which you have not yet created. Since you do not have one, select [Cancel]. Now you will see an alert box asking you if you would like to create a new BBS (fig. 2). Select "YES". -------- The System editor will have a lot of questions dealing with the configuration of your BBS. Refer to the SYSEDITG.TXT file for further information. Be sure to copy the default data files (included on your master disk) to their proper folders. This is the most common mistake made, so be sure to copy them: PROMPT.DAT - into your MENUS0 folder (Inside the TEXT folder) COMMAND.DAT, MASKS.DAT, PROTOCOL.DAT - into your DATA folder BE SURE to copy all of the files in the MENUS0 folder (On your master disk) into the MENUS0 folder on your hard drive. You should now be able to run the TRANSBBS.PRG file. After doing so, the BBS will go into a logon immediately. At that time fill in your own information. After the logon is complete, you may want to edit your own information, to increase your access. To do this, press Function key #3. Select "ONLINE USER", and begin editing. Be sure to WRITE TO DISK when your done. OTHER INFORMATION The New Menu Processor: [=====================] The new version of Transcendence now has new text handling routines, and a new menu processor. This new menu processor should fix any problems you have had with menus inside of menus, and has many new options. This new menu processor is quite similar to the old one, and should work with modifying your old menu files. But there are many changes, so be sure to read all of this file. For those of you who are new to "menu processing", it is a simple way of creating easy to use "Menus" for the user to make selections from. The menus are ASCII files that you create. A menu could contain several text files for the user to view. They may contain online games for the user to play. The options are quite endless, as you will see. As before the first three lines of a menu describe how it should work. The first line is the "options" line. It describes if it is a menu, if the user can ABORT it, what level you need to access it, and many other things. The second line is your "prompt" line. It is the prompt that the user will see after the menu is displayed. The third line is the number of selections in that menu. After the first three lines is your "selections list." This list is as long as you specified in line #3. After the list is complete you will put the actual menu that the user sees. If your new at this, your probably lost right now. Hang in there, you'll get it... The "options" line (Line #1) [--------------------------] The options line must start with "MENU" or "TEXT". ("TEXT" menus are explained later). After that you can place any of these modifiers in any order: NOABORT The menu can NOT be aborted with ^C if this modifier is used. NOPAUSE The menu can not be paused with ^S. LEVEL_xx The user must have a MENU level of at least "xx" to see/use the menu (xx can be any number from 0 to 255). AGE_xx Simlilar to the previous, but it reflects the users age. If you use "AGE_18" the user would have to be 18 years old to see/use the menu. MONLY Only MALE users can see/use the menu. FONLY Only FEMALE users can see/use the menu. examples: "MENU NOABORT LEVEL_100" (Only Users with a menu level of 100 could see this menu, and they couldn't abort it.) "MENU AGE_18 NOPAUSE FONLY" (Only users 18 years, or older, and only female users. The menu also could not be paused with ^S.) The selection line (Line #2) [--------------------------] The selection line is whatever you want it to be. Usually it is just something simple like "Make your selection: ". The menu selections [-----------------] You may have up to 256 selections for each of your menus. The number you are going to have should be in line #3. The forth line begins your selections list. This list will tell the BBS how to handle the menu. You can have four types of selections from a menu. The syntax for an selection looks like this: key type filename [Return? Y/N] Special ^ ^ ^ ^ ^ | | | | \_____ This field changes for | | | | different commands. | | | \____ Display a return prompt after the user makes | | | his/her selection (Not usable with all types) | | \____ The "filename" field is simply a filename to be used | \____ There are four different "Types" of selections a user can | make, they are explained below. \____ The "key" field is the key press (Or series of) the user has to make to access that selection. The different "types": "P" (Or 'B'): If this character is used in the TYPE field, then you are telling the menu to perform a command normally only performed from the command tables. With this you could have menu options to page the sysop, leave feedback, or just about anything. In the "Filename" field you place the filename of the command you want it to perform. Refer to the command tables section of your documentation for a list of all the different ones. The "RETURN" field can be a "Y" or a "N". If it is a "Y" (The default) it will ask the user to press RETURN before going back to the menu. The special field is not used. "C" (Or 'E,X'): This will make the menu run an external program (For example an split-screen chat program). In the filename field you put the complete pathname of the file to run (If you do not include a path it will look in the modules folder), and the special field is the TTP line for that file. The "return" field is used the same as in the above. "T" (Or "M"): This will allow you to display text files (Or more menu files!) from within your menu. In the filename field put the complete pathname of the text/menu file (If you do not include the path then it will look inside of your MENUSx folder). You can have menus inside of menus, but the limit is 25. You will get an error message if you try to go over that limit. The return is used the same as in the above example, and there is no "special" field. "O" (Or "G"): This will allow you to run a online game from within your menu. The "return" field is NOT used when you are using this selection. The filename is the complete pathname of the online game (If you do not include the path it will look in your modules folder). The "return" field is used to tell the MENU what type of online game it is. ("FOREM", "TURBO" etc.) The "special" field is the TTP line for that online game. Other things to know about menus [------------------------------] In order to get out of a menu you must have an exit command. Your exit command is part of your selections list. When you make an exit command you only use the "Key" & "Type" fields. For example the key field may be "Q" and the type field would be "exit". You can also use "exitall", this variation will make it exit ALL the menus it is in (If you have menus inside of menus). In all of the above examples all of the "key" fields have been one character long. You can have "key" fields longer than one character, except for one reserved work which is "DEFAULT". If you have the word "DEFAULT" in your "Key" field that command will be executed if the users keypress did not match ANY of the other "key" fields. A good example of this is using the key field as "DEFAULT" and the type field as "EXIT". If the user makes a selection not listed it will exit the menu. Also if you use the '@' character in the key field it is considered a "Return". Since you can not put the return character in the key field, '@' is used. Now for some examples [-------------------] In the following example the menu has 5 selections, four of them are text files, the last is an exit command: MENU Selections [Press return to exit]: 5 A t C:\BBS\TEXT\LOVE.TXT B t C:\BBS\TEXT\MONEY.TXT C t C:\BBS\TEXT\CARS.TXT D t C:\BBS\TEXT\BBS.TXT DEFAULT EXIT {1}Example Data Base [A] Meet the women of your dreams [B] How to make $1,000,000.00 in just 2 weeks [C] Best buys on cars in 1992 [D] National BBS Listing (Updated 1/20/1990) Thats all there is to it. If the user selects A,B,C,D they will see the proper file. Selecting anything else will exit the menu (Even just pressing return). (Note: The first line only contained the word "MENU"--You do not have to use the modifiers if you do not need them for that menu). (Also note: the "Return" field was not used in that example, not using it defaults to ON for each selection.) ----------------------------------------------------------------------- In this example the menu will give the user three different ways to page the sysop. MENU NOABORT LEVEL_50 Whats it gonna be (Q=Exit)? 4 1 c C:\BBS\SPITSCRN.PRG N 2 c D:\BBS\CHITCHAT.PRG N 3 p PAGESYS N Q exit {1}Chat modes: [1] Split Screen Chat (Vt52) [2] Split Screen Chat (Vt100/ANSI) [3] Normal Chat [Q] Exit Menu In the above example the user can not abort the menu, and has to have a menu level of 50 to see it. The "return" field was used in this example. Since "N"'s were placed in the "return" field the user will not be prompted to "PRESS RETURN" after the selections. ----------------------------------------------------------------------- In this example the menu allows the user to see game-oriented text files, and play an online game. MENU AGE_15 Selection: 5 1 t C:\BBS\SEE\TODAY.NEW 2 t C:\BBS\SEE\YESTER.NEW 3 t C:\BBS\SEE\SCORES.TXT @ o C:\BBS\SEE\SEE.TTP FOREM Q Exit {1}Space Empire Elite [================] [1] Todays News [2] Yesterdays news [3] Players scores [Q] Quit (Press RETURN to play Space Empire) In the above example the '@' character is used to play the game. Remember the '@' character is the same as "RETURN" while using menus. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Last minute update/note [---------------------] There is now another way to handle Online Games from within menus. This new method allows you to set up your online games almost anyway you want. With Transcendence you can have up to 99 different ONLINExx.DAT files on your hard drive. To use this feature create an ONLINExx.DAT file that you are not currently using (Lets say ONLINE2.DAT). From the menu processor you can load that ONLINE2.DAT file, and make it run that game. Since you can place more information about the game in an ONLINExx.DAT file this is more useful than using the one-line command normally used by the menu processor. Here is an example menu: MENU Selection: 6 1 t G:\TRANS\MODULES\wrestle\TODAY.txt 2 t G:\TRANS\MODULES\wrestle\YESNEWS.TXT 3 t G:\TRANS\MODULES\wrestle\CHAMP.TXT 4 t G:\TRANS\MODULES\wrestle\SCORE.TXT 5 o 1 DEFAULT exit {1}FoReM Federation Westling! [][][][][][][][][][][][][] [1] Todays news [2] Yesterdays news [3] Champion [4] Scores [5] Play Federation Wrestling! To use this feature you use "O" as the TYPE, and simply the ONLINExx.DAT number. Thats it. Pretty simple, huh? Another last minute thing: []======================[] You can now place an access level after each "type" field, for example you could use "p10" -- The user would have to have an access level of 10 or higher to use that option. BBS PROCEDURES These are the built in routines that Transcendence recognizes. The names as they should appear are followed by the page number that they are allowed on. Page 1 - Main Menu Page 2 - File Areas Page 3 - Message Bases * - All Areas Command Area Comments ------------- ---- ------------------------------------------------------ ARCUTILS 2 This will allow the user access to the Arc Utilities Section. BASEINFO 3 This will allow the user to obtain information about the message base. It includes, Base's Name, number of messages, High Message read by user, etc. BTCHSEND 2 This allows the user to download files that were marked fo batch download. CALLSYS * Allows user to Page the Sysop CATALOG 2 This allows the user to do a Catalog listing of files. CHECKM 3 This allows the user to check for messages, To, From them or both. DOWNLOAD 2 This allows the user to download files. EMAIL * This allows the user to enter the E-mail section and post E-mail. ENTERMSG 3 This allows the user to enter/post a message. EXITFILS 2 This allows the user to Exit the File Areas. EXITMSG 3 This allows the user to Exit the Message Bases. FEEDBACK * This allows the user to send feedback to the Sysop FILES 1 This allows the user to enter the File Areas. FILOCATE 2 This allows the user to Locate a File which searches all files areas available to him/her for a particular file. FSYSOP 2 Used to enter Sysop's File Maintainence section. GOODBYE * Allows the user to logoff. JUMPBASE 1 Allows the user to jump to a different base. The difference between this command and OTHERMSG is that it will only ask the user for the message base number and not display the list of available message bases. LISTING 2 Allows the user to obtain a listing (long) of files available. MACROS * Allows the user to define macros. MARKBASE * Allows the user to mark the bases that he wishes to be scanned when scanning for ne messages, etc. He/she will not be able to mark the bases that are not available to him/her. MARKFILE 2 Same as MARKBASE except for the File Areas. MARKREAD 3 Hmmm... MESBASE 1 Allows the user to Enter the message bases. MKDESC 2 Replaced with FSYSOP. MTOPIC 3 Allows the user to view the Topic Description fo a message bases if you have one defined. NEWFILES 2 Allows the user to search for New Files. NEW_MSG 3 Allows the user to search for New Messages. NEXTBASE 3 Allows the user to go to the Next Available message bases without being shown the list of available message bases or be asked which base to go to. NEXTSIG 2 Same as NEXTBASE except for the file areas. ONLINE * Allows the user to enter the Online Games menu. Play Games!! OTHERBBS * Allows the user to view/enter the Other BBSes list. OTHERMSG 3 Allows the user to Choose another message base to go to and will display the list of available Bases. OTHERS 2 Same as OTHERMSG except for File Areas. PARMEDIT * Allows the user to edit his/her parameters. PREVBASE 3 Allows the user to go to the Previous Messages base. Q_SCAN 1 Allows the user to Quick Scan the message bases. READBACK 3 Allows the user to read messages backwards. READFILE 2 Allows the user to read a text file online. READFORW 3 Allows the user to read messages foward. READMSG# 3 Allows the user to read a certain message number. RINGBACK * Allows the user to choose the Ringback feature. The BBS will hang up the user and then call him/her back. SCANEDIT * Allows the user to define which file areas to scan for new files, etc. SEARCH 2 Allows the user to search the contents of a file's description, uploader or filename for a particular string of characters. SEARCHM 3 Same as above except for messages. SECRTARY * Same as CALLSYS except the BBS ask for a reason you are paging the sysop. SETHIGH 3 Allows the user to set his/her high message read counter. SETTINGS * Allows the user to change their definable settings. SINCEDTE 2 Allows the user to search for files that were uploaded past a certain date. SURVEY * Allows the user to take a survey. SYSOP * Used to enter Sysop Mode. TERMINAL * Allows the user to select a different Terminal emulation. UEDITOR * Used to go to the User Editor. UPLOAD 2 Allows the user to upload a file. USERLIST * Allows the user to obtain a user listing. USERMES * Allows the user to leave a message for the next callers. VIEWCALL * Allows the user to view the last xx callers to the BBS. VIEWMARK 2 Allows the user to view the files that he/she has marked for batch download. VARIABLE TAGS Place the variable tags in braces ( '{' and '}' ). You can use variable tags in any of your text files, or prompt files. An example would be "Hello, {2}, how are you?" -- The BBS would change {2} into the current users handle. TAG # Description []=============================================================[] 1 Clear Screen 2 User Handle 3 REAL Name 4 Password 5 Address 6 City 7 Zip Code 8 Phone # 9 CPU 10 Age 11 Country 12 Birthday 13 Number of messsages entered by user 14 User's video width 15 User's video length 16 Emails Sent 17 User Number 18 Downloads 19 Uploads 20 DL:UL Ratio 21 Time Limit Per Day 22 Time Limit Per Call 23 Time Used Today 24 Last Date Called 25 First Date Call 26 User's number Of Calls 27 Today's Date 01/01/92 28 Today's Date Jan. 1, 1992 29 User's Command Table Level 30 Number of System Calls 31 Last Caller 32 Calls Today 33 Current baud 34 Current Time 35 User's Time Left 36 User's Connect Time 37 Military Time 38 Prompt for MORE 39 Sysop Name 40 BBS Version # 41 BBS Name 42 BBS Node # 43 Chat mode Status 44 Emails to you 45 File Area Level 46 Sex 47 Press [Return] 48 Press [Space] 49 User's Daily Call Limit 50 30 51 User's Downloads per call 52 User's Uploads per call 53 User's Downloads per day 54 User's Uploads per day 55 User's Downloads today 56 User's Uploads today 57 User's Command Table Level 58 User's State 59 Number of users allocated in userlog 60 Number of user slots in use in userlog 61 Number of new users 62 Number of surveys taken (User) 63 Number of Fmails sent (User) 64 Number of Fmsgs Sent (User) 65 Number of games played (User) 66 Number of feedbacks (User) 77 Number of messages entered (User) 78 Number of Emails Sent (User) 79 Number of uploads (System) 80 Number of downloads (System) 81 User's Status (Alert or Normal) 82 User's max number of emails per day 83 User's max number of messages per day 84 User's max number of feedbacks per day 85 User's max number of pages per day 86 User's Online Game Level 87 User's Menu Processor level 88 User's download points 89 User's number of illegal hangups 90 User's last date they listed new files 91 System's Use Only 92 " " 93 " " 94 " " 95 Number of Email Messages Waiting for User 96 Temporary holder (System's use only) 97 User's second phone number ' ' ----- Message Base Variable Tags ' 201 Message Number 202 Lines in Current Message 203 Message Base name 204 From 205 To 206 Date 207 Time 208 Subject 209 Replies 210 Status 211 New Messages 212 High message number 213 Max number of messages allowed in base before rollover occurs 214 Max number of lines allowed in message before it's extended ' ' ------ File Section variable Tags ' 300 File Area # 301 File Area Name 302 Number of Files Marked for Batch DL 303 File name 304 File size 305 File Type 306 Uploader 307 Upload Time 308 Upload Date 309 Last Downloaded Date 310 Number of Downloads 311 File Level 312 File Status 313 CPU Type 314 Monitor Type 315 File Description 316 Approx. Time to Download at {33} (Baud) 317 Used for Blank Space 318 Default Protocol 319 Current Protocol used 320 Number of Descriptions/Files 321 Approx. Time to Download Marked Files 322 File Number 323 Not used at Moment 324 Xmodem Blocks 325 Y/Zmodem Blocks 326 Fmodem Blocks **** These are for System's Use Only 327 CPS Rating 328 Old Filename. Used during file renames 329 New Filename. " " 330 Max number of allowed uploads 331 Max Upload size. Most available Space on Drive.